---
id: 65b28add2c939e25b1d9b0e1
title: Task 42
challengeType: 19
dashedName: task-42
audioPath: curriculum/js-music-player/We-Are-Going-to-Make-it.mp3
---

<!--
AUDIO REFERENCE: 

Previous line: Sarah: Well, I was investigating the code when I saw that the problem might be related to the recent updates.
Current line: Sarah: I tried rolling back to the previous version, but it didn't fix the issue.
-->

# --description--

Understanding how different steps in solving a problem are connected is key.

# --question--

## --text--

How do Sarah's two actions of looking at the code and going back to an older version connect?

## --answers--

Looking was to find the problem; going back was for a new change.

### --feedback--

Both steps were to solve the issue, not for new changes.

---

Both were ways to try and solve the same problem.

---

Looking was for a report; going back was to solve the problem.

### --feedback--

Both steps were aimed at fixing the issue, not reporting.

---

Looking was her first try, and going back was not linked.

### --feedback--

Going back was related to her first step and part of trying to solve the issue.

## --video-solution--

2
